Note

Medium Risk
Touches new-thread draft creation/reuse logic and draft-store cleanup rules, which can impact routing and draft persistence across projects. Changes are localized and covered by new unit and browser-level tests, reducing regression risk.

Overview
New-thread draft reuse is tightened for worktree defaults and promotion in-flight. When the project default env mode is worktree, sidebar seed context now forces envMode: "worktree" instead of inheriting an active thread’s branch/worktree path, ensuring the next thread starts as a fresh worktree draft.

Draft reuse/cleanup is also guarded so promoting draft threads aren’t reused or deleted mid-promotion (useHandleNewThread checks promotedTo == null; composerDraftStore won’t evict a prior draft if it’s promoting). Adds regression coverage in ChatView.browser.tsx and Sidebar.logic.test.ts.

^{Reviewed by Cursor Bugbot for commit 33d6b03. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix new-thread draft reuse when the default environment mode is worktree

• Fixes two bugs in the new-thread flow: promoting drafts were being reused instead of creating a new draft, and worktree-defaulted projects were inheriting branch/path context from active threads.
• In useHandleNewThread.ts, draft reuse is now skipped when the active draft has already been promoted (promotedTo != null).
• In composerDraftStore.ts, deletion of a previous logical-project draft is skipped when that draft is in a promoting state.
• In Sidebar.logic.ts, resolveSidebarNewThreadSeedContext returns { envMode: 'worktree' } immediately when defaultEnvMode is 'worktree', ignoring any active thread context.

^{Macroscope summarized 33d6b03.}